Tool for generating event case management applications

ABSTRACT

A system for generating event case management applications. The system requires input of event case criteria, such as, but not limited to, event case type, steps, actions associated with the steps, actors required to perform the actions, data entry documents/forms and/or data entry elements in the documents/forms, and data entry points. Based on the received inputs and rules associated with the event case type and other event case criteria, the tool automatically generates computer code that creates an event case management application. As such, the tool provides a standardized and streamlined approach to generating event case management applications that requires minimal technology support, is cost efficient and effectively delivers deployable event case management applications in minimal time.

FIELD OF THE INVENTION

The present invention is generally directed to computer processing and,more specifically, automatically generating computer code for event casemanagement applications using a streamlined approach for receivingcriteria that defines the process for resolving the event case.

BACKGROUND

In a large enterprise many different issues or problems, referred toherein as event cases, may arise that require resolution. Each of thedifferent types of event cases or, in some instances, each event caserequires a different approach for resolving the event case. In otherwords, different steps and/or actions must be taken to resolve eachdifferent type of event case. Moreover, the enterprise is likely to haveapplicable rules, both internally-driven and externally driven rulesthat dictate how the event case is to be resolved. Such rules may bedictated by the type of event cases, as well as other specificsassociated with the event case, such as, but not limited to, actionsrequired, actors performing the actions, the type of data required to becollected and the like.

In most instances, each of the different types of event cases will haveindividual computer applications, otherwise referred to as programs,modules, tools or the like for managing the event case resolutionprocess. Such individual applications are necessary based on each typeof event case requiring steps and/or actions to resolve the case,including different requirements in terms of data collection and thelike. Typically, applications, such as event case managementapplications are built in a web-based, collaborative platform thatallows for multiple entities to interact in the application buildingprocess. However, such collaborative environments typically pose acompliance issue, in that, the platform exposes a high volume ofsensitive material, such as non-public information or the like, to manydifferent application developers. More secure development ofapplications can be made possible through use of other platforms, suchas a class-based, object-oriented general purpose programming languageplatform; however, typically such development has an extended periodfrom concept to market (e.g.. six to twelve months or the like) and tendto be cost prohibitive. In addition, such platforms aretechnology-driven and require a dependency on technologypartners/support.

Therefore, a need exists to develop systems, methods and the like fordeveloping and generating event case management applications forindividual event cases or event case types. The desired systems, methodsand like should be capable of generating any and all event casemanagement applications across an entire enterprise while at the sametime taking into account event case management rules that may bespecific to segments of the enterprise, event case type and other eventcase management factors. Moreover, since the individual case managementapplications tend to be less complex applications, the desired systems,methods and the like should offer a solution that requires less in termsof technical support, for example, leveraging a standard technologystack or the like. Additionally, the desired systems, methods and likeshould provide for generating the event case management applications ina timely fashion so as to reduce the time from conception toimplementation. In addition, the desired systems, methods and likeshould provide a cost advantage over current application developmentsolutions.

BRIEF SUMMARY

The following presents a summary of certain embodiments of theinvention. This summary is not intended to identify key or criticalelements of all embodiments nor delineate the scope of any or allembodiments. Its sole purpose is to present certain concepts andelements of one or more embodiments in a summary form as a prelude tothe more detailed description that follows.

Embodiments of the present invention address the above needs and/orachieve other advantages by providing systems, methods, computer programproducts and like for generating event case applications for managingthe process for resolving an event case. Event case, as used herein, isa problem or issue triggered by an event that requires a systematicframework (i.e., process) for resolving the problem or issue. In a largeenterprise, a vast amount of different types of event cases each requirea different process for resolving the event based on different steps andactions that must be taken to resolve the case and different internaland external rules that govern how the event case needs to be resolved.

The present invention provides a standardized means for generating eventcase applications regardless of event case type and/or the rulesgoverning the event case type. In addition, the present invention iscapable of automatically generating computer code that createssimplified event case management applications with minimal need fortechnology support or dependency on technology partners. Additionally,by instantaneously generating an initial event case application whichserves as, at least, a prototype, the present invention is able tosignificantly reduce the time from conception to implementation.Moreover, the simplified approach of the present invention is able togenerate event case management application in a cost efficient manner.

The present invention provides for a tool in which users input requisiteevent case criteria, such as steps, actions, sequencing of the steps,identification of data entry documents and associated data entryelements, as well as the steps and or actions associated with the dataentry documents and/or entry elements and, based on rules applicable toat least the event case type, generates computer code that creates anapplication for managing the event case.

A system for generating event case management applications defines firstembodiments of the invention. The system includes a first computingplatform including a first memory and at least one first processor incommunication with the first memory. The system further includes anevent case management application rules database that is stored in thefirst memory. The database stores rules for generating an event casemanagement application, wherein the rules are specific to at least casetype and, in other alternate embodiments of the invention, the rules maybe specific to one or more of (i) actions associated with steps of theevent case, (ii) actors assigned to perform the actions, (iii) the dataentry documents and/or (iv) data elements required in the event case orthe like.

The system additionally includes a second computing platform including asecond memory and at least one second processor in communication withthe second memory. An event case management application generator toolis stored in the second memory and executable by the at least one secondprocessor. The tool is configured to receive inputs that define criteriaincluding case type for managing an event case. In response to receivingthe user inputs, the tool is configured to access the rules database toobtain one or more rules specific to the case type and, in optionalembodiments, specific to one or more of (i) actions associated withsteps of the event case, (ii) actors assigned to perform the actions,(iii) the data entry documents and/or (iv) data elements required in theevent case. Further, the tool is configured to apply the user inputs andone or more rules to automatically generate computer code that createsan application for managing the event case.

In specific embodiments of the system, the event case managementapplication generator tool is further configured to receive the inputsthat define the criteria for managing the event case, wherein the inputsdefine a plurality of steps required to resolve the event. In suchembodiments of the system, the inputs include, for each of the pluralityof steps, at least one of (i) a step identifier, (ii) an actor forperforming the step, (iii) actions required to perform the step, and(iv) an estimated time for completing the step.

In other specific embodiments of the system, the event case managementapplication generator tool is further configured to receive the inputsthat define the criteria for managing the event case, wherein the inputsdefine a sequence/flow for interconnecting the plurality of steps. Insuch embodiments of the system, the inputs include creating paths forinterconnecting the plurality of steps and the actions required toperform the steps.

In other specific embodiments of the system, the case managementapplication generator tool is further configured to receive the inputsthat define the criteria for managing the event case, wherein the inputsdefine one or more predetermined data entry documents and one more dataelements within each of the predetermined data entry documents. In suchembodiments of the system, the inputs define at least one of the stepsor the actions that are associated with at least one of the one or moredata entry documents or at least one of the data elements within the atleast one of the data entry documents (i.e., the points in the processwhere data is required to be collected).

In other specific embodiments of the system, the case managementapplication generator tool is further configured to generate thecomputer code that creates the application for managing the event case,wherein the application includes a plurality of user interfaces formanaging a workflow for processing the event case. In other specificembodiments of the system, the application includes a process model thatdefines the steps and the actions required to perform the steps.

A computer-implemented method for generating event case managementapplications defines second embodiments of the invention. The method isexecuted by one or more computing device processors and includesreceiving inputs that define criteria, including case type, for managingan event case, wherein an event case is defined as a process forresolving an event that requires a resolution. The method furtherincludes, in response to receiving the user inputs, accessing a rulesdatabase to obtain one or more rules specific to the case type.Additionally, the method includes applying the inputs and the one ormore rules specific to at least the case type to automatically generatecomputer code that creates an application for managing the event case.

In specific embodiments of the method, receiving the inputs that definethe criteria for managing the event case further includes receivinginputs that define a plurality of steps required to resolve the eventand, for each of the steps, at least one of (i) a step identifier, (ii)an actor for performing the step, (iii) actions required to perform thestep, and (iv) an estimated time for completing the step.

In other specific embodiments of the method, receiving the inputs thatdefine the criteria for managing the event case further comprisesreceiving inputs that define a sequence for interconnecting theplurality of steps including creating paths for interconnecting theplurality of steps and the actions required to perform the steps.

In still further specific embodiments of the method, receiving theinputs that define the criteria for managing the event case furthercomprises receiving inputs that define one or more predetermined dataentry documents and one more data elements within each of thepredetermined data entry documents and at least one of the steps or theactions associated with at least one of the one or more data entrydocuments or at least one of the data elements within the at least oneof the data entry documents.

In other specific embodiments of the method accessing the rules databaseto obtain one or more rules further comprises accessing the rulesdatabase to obtain one or more rules specific to at least one of stepsrequired to process the event case, actions required to perform thesteps, actors required to perform the actions, data entry documents ordata entry elements within the documents.

A computer program product including a non-transitory computer-readablemedium defines third embodiments of the invention. The computer-readablemedium includes a first set of codes for causing a computer to receiveinputs that define criteria, including case type, for managing an eventcase. The computer-readable medium additionally includes a second set ofcodes for causing a computer to, in response to receiving the userinputs, access a rules database to obtain one or more rules specific tothe case type, and a third set of codes for causing a computer to applythe criteria and the one or more rules specific to at least the casetype to automatically generate computer code that creates an applicationfor managing the event case.

Thus, according to embodiments of the invention, which will be discussedin greater detail below, the present invention provides for a tool forgenerating event case management applications. The tool requires inputof event case criteria, such as, but not limited to, event case type,steps, actions associated with the steps, actors required to perform theactions, data entry documents/forms and/or data entry fields in thedocuments/forms, and data entry points. Based on the received inputs andrules associated with the event case type and other event case criteria,the tool automatically generates computer code that creates an eventcase management application. As such, the tool provides a standardizedand streamlined approach to generating event case managementapplications that requires minimal technology support, is cost efficientand effectively delivers deployable event case management applicationsin minimal time.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 provides a schematic diagram of a system for generating eventcase management applications, in accordance with embodiments of theinvention;

FIG. 2 provides a block diagram of an apparatus configured forgenerating event case management applications, in accordance withembodiments of the invention;

FIG. 3 provides a flow diagram of a method for generating event casemanagement applications, in accordance with embodiments of theinvention; and

FIGS. 4-24 provide various user interfaces used for generating an eventcase management application; in accordance with embodiments of theinvention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

As will be appreciated by one of skill in the art in view of thisdisclosure, the present invention may be embodied as an apparatus (e.g.,a system, computer program product, and/or other device), a method, or acombination of the foregoing. Accordingly, embodiments of the presentinvention may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.), or an embodiment combining software and hardwareaspects that may generally be referred to herein as a “system.”Furthermore, embodiments of the present invention may take the form of acomputer program product comprising a computer-usable storage mediumhaving computer-usable program code/computer-readable instructionsembodied in the medium.

Any suitable computer-usable or computer-readable medium may beutilized. The computer usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, ordevice. More specific examples (e.g., a non-exhaustive list) of thecomputer-readable medium would include the following: an electricalconnection having one or more wires; a tangible medium such as aportable computer diskette, a hard disk, a time-dependent access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM or Flash memory), a compact disc read-only memory(CD-ROM), or other tangible optical or magnetic storage device.

Computer program code/computer-readable instructions for carrying outoperations of embodiments of the present invention may be written in anobject oriented, scripted or unscripted programming language such asJAVA, PERL, SMALLTALK, C++ or the like. However, the computer programcode/computer-readable instructions for carrying out operations of theinvention may also be written in conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages.

In specific embodiments of the invention the tool for generating eventcase management applications is built on a business process management(BPM) platform, such as PEGA 7 platform for application development.Such capabilities provide for the user to generate an event casemanagement application absent the need for technology involvement.

Embodiments of the present invention are described below with referenceto flowchart illustrations and/or block diagrams of methods orapparatuses (the term “apparatus” including systems and computer programproducts). It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a particular machine, such that the instructions, which executeby the processor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instructions, whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational events to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions, which execute on the computer or other programmableapparatus, provide events for implementing the functions/acts specifiedin the flowchart and/or block diagram block or blocks. Alternatively,computer program implemented events or acts may be combined withoperator or human implemented events or acts in order to carry out anembodiment of the invention.

As the phrase is used herein, a processor may be “configured to” performa certain function in a variety of ways, including, for example, byhaving one or more general-purpose circuits perform the function byexecuting particular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

Thus, according to embodiments of the invention, which will be describedin more detail below, event case applications are generated for managingthe process for resolving an event case. Event case, as used herein, isa problem or issue triggered by an event that requires a systematicframework (i.e., process) for resolving the problem or issue.

The present invention provides a standardized means for generating eventcase applications regardless of event case type and/or the rulesgoverning the event case type. In addition, the present invention iscapable of automatically generating computer code that creates asimplified event case management application with minimal need fortechnology support or dependency on technology partners. Additionally,by instantaneously generating an initial event case application whichserves as at least a prototype, the present invention is able tosignificantly reduce the time from conception to implementation.Moreover, the simplified approach of the present invention makes itpossible to generate event case management applications in a costefficient manner.

The present invention provides for a tool in which users input requisiteevent case criteria, such as steps, actions, sequencing of the steps,identification of data entry documents and associated entry elements, aswell as the steps and or actions associated with the data entrydocuments and/or entry elements and, based on rules applicable to atleast the event case type, generates computer code that creates anapplication for managing the event case.

Referring to FIG. 1 a schematic diagram is shown of a system 100 forgenerating event case management applications, in accordance withembodiments of the invention. The system 100 is implemented in adistributed computing network 200, which allows for computerizedcommunication of data between different computing platforms, apparatus,devices and the like. The distributed computing network 200 may comprisethe Internet, one or more intranets and/or a combination of the Internetand one or more intranets.

The system 100 includes a first computing platform 300, which maycomprise one or more computing apparatus and/or devices, such asservers, storage components and the like. The first computing platform300 includes a first memory 302 and at least one first processor 304 incommunication the first memory 302. The first memory 302 stores eventcased management rules database 306 that includes rules for generatingevent case management applications. The rules may be internal rulesconfigured by the enterprise and/or external rules (i.e., regulatoryand/or compliance rules configured by a government entity or the like).At a minimum, according to embodiments of the invention, the rulesinclude case-type rules 308 that are based on the type of case beinginvestigated (e.g., customer complaint, account, misappropriation or thelike). In alternate embodiments of the invention the rules may include,but are not limited to, action-type rules 310, actor-type rules 312,document/form-type rules 314, data element-type rules 316 and the like.Action-type rules 310 are based on the actions assigned by the user(i.e., event case management application generator) required to conductthe event case management process. Actor-type rules 312 are based on theactor (i.e., entity/individual) assigned by the user to perform anaction or step. Document/form-type rules 314 are based on thedocuments/forms that are assigned to the event case management processby the user and data element-rules 316 are based on the individual dataelements/items, typically located in the documents/forms, that areassigned to the event case management process by the user.

The system 100 additionally includes second computing platform 400 whichis in network communication with the first computing platform 300 viadistributed computing network 200. Similar to the first computingplatform 300, the second computing platform 400 may comprise one or morecomputing apparatus and/or devices, such as servers, storage componentsand the like. Moreover, while first and second computing platforms 300and 400 are shown and described as separate physical entities, they maybe configured as one physical computing platform and/or share in the useof individual components of the computing platforms. The secondcomputing platform 400 includes a second memory 402 and at least onesecond processor 404 in communication the second memory 402. The secondmemory 402 stores event case management application generator tool 406,which according to specific embodiments of the invention may be built ona business process management (BPM) platform, such as PEGA 7 platformfor application development. Such platforms provide for the user togenerate an event case management application with minimal to notechnology involvement.

The event case management application generator tool 406, heretoforereferred to as the “tool” 406 is configured to receive a plurality ofinputs 408 that define application criteria 410. The inputs may bereceived from a user or from auxiliary systems (not shown in FIG. 1)that support the generation of event case management applications 416.The application criteria 410 includes case type 412, which may bedefined by a case name, a case identifier and/or a case description. Inadditional embodiments of the invention, the application criteria 410may include, but is not limited to, steps required to perform the eventcase management process, action(s) required to perform a step, actorsrequired to perform an action or step and estimated time to complete astep or action. In additional embodiments of the invention, theapplication criteria 410 may include, but is not limited to, thesequence for performing the steps (i.e., how each step and/or actioninterconnects to one or more other steps and/or actions), the documentsand/or forms required from a data collection standpoint, as well as, theindividual data elements within the documents/forms and the data points(i.e., the step or action within the process at which the document/formis applicable or an individual data element is applicable).

In response to receiving the inputs 408, the tool 406 is furtherconfigured to access the event case management rules database to obtainone or more rules associated with the inputs 408. At a minimum, the tool406 is configured to obtain case-type rules 308 associated with thedefined case type 412. In alternate embodiments of the invention, thetool 406 is configured to obtain one or more of action-type rules 310,actor-type rules 312, document-type rules 314 and/or data element-typerules 316.

Additionally, the tool 406 is configured to apply the applicationcriteria 410 and the rules 310-316, to generate computer-code 414 thatcreates an event case management application 416 for managing the eventcase. The application 416 includes a series of user interfaces withvarious data entry fields, which form the basis for the event casemanagement process. An event case management administrator or the likemanages the event case by providing inputs into the various data entryfields as a result of performing the steps, actions and data collectionrequired by the event case management application 416.

Referring to FIG. 2 a more detailed block diagram of the secondcomputing platform 400 is depicted, in accordance with embodiments ofthe present invention. In addition to providing more details for theevent case management application generator tool 406, FIG. 2 providesvarious optional embodiments of the system. The second computingplatform 400, which may comprise one or more apparatus, devices isconfigured to execute algorithms, such as modules, routines,applications and the like. Computing platform 400 includes memory 402,which may comprise volatile and non-volatile memory, such as read-onlyand/or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards,or any memory common to computer platforms). Moreover, memory 402 maycomprise cloud storage, such as provided by a cloud storage serviceand/or a cloud connection service.

Further, computing platform 400 also includes processor 404, which maybe an application-specific integrated circuit (“ASIC”), or otherchipset, logic circuit, or other data processing device. Processor 404may execute an application programming interface (“API”) (not shown inFIG. 2) that interfaces with any resident programs, such as event caseapplication generator tool 406 or the like stored in the memory 402 ofthe computing platform 400.

Processor 404 may include various processing subsystems (not shown inFIG. 2) embodied in hardware, firmware, software, and combinationsthereof, that enable the functionality of the computing platform 400 andthe operability of the computing platform 400 on the distributedcomputing network 200 (shown in FIG. 1). For example, processingsubsystems allow for initiating and maintaining communications andexchanging data with other networked devices. For the disclosed aspects,processing subsystems of processor 404 may include any subsystem used inconjunction with event case application generator tool 406 and relatedsub-routines, algorithms, sub-algorithms, modules, sub-modules thereof.

Computer platform 400 may additionally include a communications module(not shown in FIG. 2) embodied in hardware, firmware, software, andcombinations thereof, that enables electronic communications between thecomputing platform 400 and other platforms, apparatus and/or devices(shown in FIG. 1). Thus, communication module may include the requisitehardware, firmware, software and/or combinations thereof forestablishing and maintaining a network communication connection.

Memory 404 of computing platform 400 stores event case managementapplication generator tool 406, which is built on a business processmanagement (BPM) platform such that a series of user interfaces arepresented that ask a user various different queries to establish theapplication criteria 410 for generating the computer code 414 thatcreates the event case management application 416.

As previously discussed in relation to FIG. 1, the event case managementapplication generator tool 406 is configured to receive, in response topresentation of the queries, a plurality of inputs 408 that defineapplication criteria 410. The inputs may be received from a user or, inalternate embodiments of the invention, from auxiliary systems thatsupport the generation of event case management applications 416. Theapplication criteria 410 includes case type 412, which may be defined bya case name/case identifier 420 and/or a case description 422. Inadditional the application criteria 410 may include, but is not limitedto, steps 430 required to perform the event case management process,including a step name/identifier 432, action(s) 434 required to performa step 430, actors 436 required to perform an action 434 (or step 430),and an estimated time 438 to complete a step or action (or other servicelevel agreement (SLA) associated information).

Additionally, the application criteria 410 may include, but is notlimited to, a sequence 440 for performing the steps 430 (i.e., how eachstep 430 and/or action 434 interconnects to one or more other steps 430and/or actions 434). The sequencing forms the methodology/flow forperforming the event case management process.

In addition, the application criteria 410 includes the documents/forms450 required from a data collection standpoint, as well as, theindividual data elements 452 within the documents/forms 450 and the datapoints 454 (i.e., the step 430 or action 434 within the process at whichthe document/form 450 is applicable or where the individual data element452 is required to be inputted/collected).

In response to receiving the inputs 408, the tool 406 is furtherconfigured to access the event case management rules database (shown inFIG. 1) to obtain one or more rules 310-316 associated with the inputs408. At a minimum, the tool 406 is configured to obtain case-typerule(s) 308 associated with the defined case type 412. In alternateembodiments of the invention, the tool 406 is configured to obtain oneor more of action-type rules 310, actor-type rules 312, document-typerules 314 and/or data element-type rules 316.

Additionally, the tool 406 is configured to apply the applicationcriteria 410 and the rules 310-316, to generate computer code 414 thatcreates an event case management application 416 for managing the eventcase. The application 416 includes a series of user interfaces 460 withvarious data entry fields, which form the basis for the event casemanagement process. As shown in FIGS. 4-24 and described infra., anevent case management administrator or the like manages the event caseby providing inputs into the various data entry fields as a result ofperforming the steps, actions and data collection required by the eventcase management application 416. In additional embodiments of theinvention, the event case management application includes a processmodel 462, which is configured to illustrate the flow/process forperforming the steps 430 and/or actions 434 that define the event casemanagement process.

Referring to FIG. 3, a flow diagram is presented of a method 500 forgenerating an event case management application, in accordance withembodiments of the invention. At Event 510, a plurality of inputs arereceived that define the application criteria for the event casemanagement process. As previously discussed the application criteriaincludes the case type (i.e., inputs that provide for a case name, acase identifier and/or a case description). Additionally, theapplication criteria may include steps required of event case managementprocess, one or more actions associated with a step, actors required toperform the actions/steps and an estimated time for completing a step oraction. Additionally, the application criteria may include thesequencing/interconnection of the steps and/or actions, which providefor the methodology/flow for performing the event case managementprocess. In addition, the application criteria may include thedocuments/forms required by the event case and the data elements withinthe documents/forms that are required, as well as the data points (i.e.,steps and/or actions) at which the data elements are required to beinputted/collected.

At Event 520, in response to receiving the application criteria, therules database is accessed to obtain one or more rules specific to atleast the case type. In other embodiments of the invention, the rulesmay be specific to action-type, actor-type, document/form-type, dataelement-type or the like. As previously noted, the rules may be rulesinternal to the enterprise or rules/standards external to the enterprise(e.g., regulatory, compliance rules or the like).

At Event 530, the application criteria and the rules are applied toautomatically generate computer code that creates an application formanaging the event case. The application comprises a plurality of userinterfaces that provides the process for event case management asdefined by the steps and actions required. In addition, the applicationmay include a process model that illustrates the overall process/flowfor event case management and shows and highlights the progress beingmade to complete the process (i.e., where the process currently residesand/or steps/actions outstanding).

FIGS. 4-24 provide various illustrations of exemplary graphical userinterfaces (GUIs) used to generate an event case management application,in accordance with embodiments of the present invention. As depicted inFIGS. 4-24, the GUIs present a user (i.e., an event case managementapplication developer) with a simplified lightweight case template forcreating customized applications to handle the various types of casesthat may arise at an enterprise. It should be noted that the GUIs asdepicted in FIG. 4-24 may be presented to the user on any number ofdevices. For example, the GUIs may be presented on a Personal Computer(PC), a desktop computer, a laptop computer, a mobile device, or thelike. The layout of the GUI as depicted in FIGS. 4-24 is by way ofexample only and, thus, may be altered in some degree to reflect thedifferent devices through which a user accesses the GUI. However, thefeatures as described herein may be present in any such embodiment.

In the GUI of FIG. 4, an initial user interface is provided from which auser can select a “create” option to initiate the process for generatingan event case management application. Specifically, as shown in FIG. 4the user may select from options “create”, “open”, and “resolved” tobegin processing a case application. The “create” option allows a userto create a new application, which may be desirable if an applicationfor handling such an event case has not yet been created by the eventcase management application generator tool (i.e., “tool”). The “open”option allows the user to open an existing application which is in theprocess of being created. The “open” may be desirable if the user hasstarted creating an application but the application has not yet beencompleted or otherwise created by the tool. The “resolved” option allowsa user to open applications that have been created, i.e., applicationsthat the tool has previously generated.

As shown in FIG. 4, the tool may be configured to provide the user withother features. For example, a user may work with additional users orteam members (i.e., a collaborative effort) in creating applications forany given case. As shown in FIG. 4, there is a menu on the right-handside of the GUI displaying “TEAM MEMBERS” if there are any suchadditional users for a given case. Moreover, the right-hand side of theGUI of FIG. 4 includes a “WORK BASKET” menu that allows a user to selectfrom Work Baskets in the event that particular cases that are in processfor generating an associated application are categorized into such workbaskets. A user may also select from recently worked on cases under the“Recent” menu depicted on the left-hand side of the GUI.

FIG. 5 depicts the GUI after a user has selected the “create” option asdetailed above. As shown in FIG. 5, in some embodiments of the inventionthe GUI features a status/progress bar indicating the progress of theuser in creating the event case management application. In FIG. 5, thestatus/progress bar indicates that the user is at Step 1—Case TypeDetails (indicated by the circle surrounding the number “1”), whilesteps 2 through 5 (Case Steps, Case Sequence, Case Forms and CaseActions) remain. The remaining steps 2-5 will be described in greaterdetail herein with accompanying figures depicting how those steps areaccomplished in the tool.

FIG. 5 also depicts an input box for a user to input applicationcriteria regarding the Case Type Name and a Case Type description. Asdescribed previously the case type application criteria may be the basisfor one or more rules that are subsequently applied when generating thecomputer code that creates the event case management application. Asdepicted in FIG. 5, these inputs may be inputted in simple text formusing a keyboard, touchpad, or other input device. In FIG. 5, andthroughout the remaining figures, some user input prompts areaccompanied by an indication that certain other application criteria isrequired. In FIG. 5, the asterisk indicates that both the Case Type Nameand Case Type Description are required inputs. The tool is configuredsuch that further progress within the tool is not possible until theuser has inputted values in the data entry field deemed to be required.

FIG. 6 depicts the Case Steps input phase of the event case managementapplication generation process. The status/progress bar indicates thatthe user is at Step 2—Case Steps (indicated by the circle surroundingthe number “2” of the status/progress bar), In the GUI of FIG. 6, thetool is configured to allow a user to define steps for resolving a caseof the Case Type defined in Step 1 and shown in FIG. 5. The GUI of FIG.6 is configured as a table-type layout where case steps are displayedonce they have been inputted by the user. The table will display atleast the Step Name, Actor Type, User Type, and Queue Name for each CaseStep inputted by the user. In the GUI of FIG. 6, Case Steps have yet tobe added by the user. However, a user may define a new Case Step byselecting the Add Case Steps option (indicated by the box-enclosed plussign “+”icon).

FIG. 7 depicts the dialog box GUI displayed to the user in response tothe user selecting the Add Case Steps option described in FIG. 6. Asshown in FIG. 7, the addition of a new Case Step includes requiredinputs for a Step Name, an Actor Type (i.e. type of individual requiredto perform the step), a Step Short Name (i.e., abbreviated name ofstep), and the User Type. The tool may be additionally configured toallow the user to also add optional application criteria relating to theDays of Service Level Agreement (SLA) (i.e., estimated time forcompleting the step) and the Queue Name. Further, the tool may beconfigured to allow the user to add Step Actions for the Actionsassociated with the Case Step, if necessary.

The Step Name and Step Short Name are titles and/or names for theindividual steps required for the particular Case Type. For example, aStep Name may be “Complaint Information” while a Step Short Name for thesame Case Step may be CompInfo. The Step Name and Step Short Name serveas indicators to the user that may suggest some details of theparticular Case Step. As shown in the GUI of FIG. 7, the Actor Type andUser Type may be selected from a drop down menu. However, it should beunderstood that it may also be inputted through other means, such asthrough text entry. The Actor Type is the type of actor/individualrequired to perform the step and/or action defined within the event casemanagement application. As shown in FIG. 7, the Actor Type may be a“User” or it may also be another type of actor, such as a “ServiceLevel” or “Queue.” Similarly, the User Type may be a “Case CreatedUser”, a “Last Updated User”, or a “Manager.” The User Type defines theindividual who will use the case management application at a particularstep.

Referring to FIG. 8, the dialog box for entering a Case Step as shown inFIG. 7 is depicted. In the dialog box of FIG. 8, the Actor Type ischanged to Queue. As shown in FIG. 8, by changing the Actor Type toQueue, the dialog box for Queue Name becomes a required field. Thus, theuser will not be able to proceed with the Case Step unless a value forQueue Name has been inputted. A Queue is defined herein as a group ofindividuals, where the step or action is assigned to the queue, suchthat a next available individual within the queue is assigned the stepand/or action.

FIG. 9 depicts the dialog box for entering a Case Step, as shown inFIGS. 7 and 8. In FIG. 9, unlike FIGS. 7 and 8, the Case Step requiresActions. Thus, as shown in FIG. 9, the user has added Actions byselecting the Add Step Actions option in the dialog box. As shown, byselecting the Add Step Actions dialog box, the user is presented with anentry form to add Actions. In FIG. 9, the Actions that have been addedare “Submit” and “Go Back,” but it should be understood than any Actionsmay be entered depending on the needs of a Given Case Step.

Referring to FIG. 10, the event case management application generationprocess has progressed to Step 3 entitled Case Sequence. Thestatus/progress bar indicates that the user is at Step 3 - Case Sequence(indicated by the circle surrounding the number “3” of thestatus/progress bar). In the Case Sequence step the tool is configuredto allow the user to define the sequence in which the Case Stepspreviously defined and discussed with respect to FIGS. 7-9 are to beexecuted in the final case application. As shown in the GUI of FIG. 10,the various previously defined Case Steps are organized with referenceto their Step Name, Actor Type, User Type, and Queue Name. Additionally,the tool is configured such that each of the Case Steps have the optionto Add Incoming Paths, wherein the user can add incoming paths to eachof the previously defined Case Steps.

FIGS. 11-12 depict an additional dialog box displayed in response to auser selecting to Add Incoming Paths to an existing Case Step. As shownin FIG. 11, the tool is configured to present a series of drop downmenus for each path the user wishes to add. The drop down menus areconfigured to allow the user to select from which Case Step the pathwill begin and through which Action associated with the Case Step thepath will go through. For example, as shown in FIG. 12, the user hasselected to add an incoming path from the approval case step, which waspreviously defined in a manner similar to that described for FIGS. 7-9.The user then selects the path to go through the action of “Reject”which was previously defined as an Action for the associated Case Stepfor Approval.

FIG. 13 depicts a GUI according to embodiments of the invention after auser has created incoming paths. The GUI shown in FIG. 13 appearssimilar to that as depicted in FIG. 10; however, the Case Step “CustomerInformation” has been expanded to display additional information aboutthe Case Step. The additional information displays the information addedduring Step 2—Case Steps and the available actions previously defined.If a user has added or changed any of this information, they have theoption to Save or Discard any changes.

Referring to FIG. 14 the event case management application generationprocess has progressed to Step 4 entitled Case Forms. Thestatus/progress bar indicates that the user is at Step 3—Case Forms(indicated by the circle surrounding the number “4” of thestatus/progress bar). In Step 4 the tool is configured to allow a userto define Case Forms/Documents and to add data elements to those CaseForms/Documents. As shown in FIG. 14, the tool is configured to allowthe user to select the Add Case Forms option to add a Case Form. Theuser may further define the Form Name and Add Form Elements to addelements to the Case Form.

FIG. 15 depicts a dialog box that is configured to be displayed to theuser in response to selection of an Add Form Elements. The dialog box isconfigured with an option for the user to Add Form Elements. In responseto activating the Add Form Elements option, the tool is configured toallow the user to enter a Data Field Name, select from a drop down menua Field Type, select a Field Format, and provide an indication as towhether the Field is a required field. Once the user has determined theparameters for the Form Element, the user can submit the Form Elementand add it to the respective Form. FIG. 16 shows the dialog box asadditional Form Elements are added to the Form. As shown in FIG. 16,some of the Form Elements have been designated as Required and have afield format as pxTextInput or TextInput. It should be understood thatother Field Formats may be appropriate for Field Types that have beendesignated as something other than Text.

After the user has entered the desired Case Forms and determined theappropriate Form Elements for each, the GUI shown in FIG. 17 isdisplayed. FIG. 17 depicts a GUI in which the event case managementapplication generation process has progressed to Step 5 entitled CaseActions. The status/progress bar indicates that the user is at Step5—Case Actions (indicated by the circle surrounding the number “5” ofthe status/progress bar). As shown in FIG. 17, the tool is configured toallow the user to add Forms to any of the Case Actions defined in theprevious input phases of the event case management applicationgeneration process. As shown, some of the Process Steps may havemultiple Actions associated with them. For example, as shown in FIG. 17,FulfillRequest has both a Submit and a Previous Action defined. Thus,the tool is configured to present two separate Add Forms options foreach of those Actions, in order to allow the user to add separate formsfor the applicable Action.

In response to a user selecting an action to add a Case Form, the dialogbox shown in FIG. 18 appears. The dialog box is configured to allow theuser to select from a prepopulated list of the Forms previously createdin step 4 and assign them to the corresponding action. The tool is alsoconfigured to allow the user to select an option to make the form ReadOnly. The Read Only option provides for the Form to be un-editable bythe application user once the application has been created.

After assigning the Forms to the corresponding actions, the user hasinput all of the necessary information for the tool to create the eventcase management application. Referring to FIG. 19, the tool isconfigured to present a GUI in which Case Content is shown as a list ofthe Case Steps, an assigned reviewer for each Case Step and the statusof the case review process. Each of the Case Steps are required to bereviewed prior to creating the event case management application.

Referring to FIGS. 20 and 21 a flow chart of the overall event casemanagement process is depicted which is configured to allow the user toview a visual representation of the case management application to becreated based on the user inputs in the above described steps. As shownin FIG. 20, the Case Steps are arranged linearly beginning with Startand ending at the End Case Step. Each Case Step is connected by theActions defined by the user and the corresponding input paths. In FIG.21, the user has separated the Case Steps to better demonstrate theprocess flow of the application. As shown in FIG. 21, the Case Steps areconnected by the previously defined Actions and input paths. Forexample, if the application is at Case Step FulReque, and the ActionFulfillRequest_Submit is completed, the case management application willmove to the Approval Case Step. At Approval, there are two possibleActions that can be taken. If the end user completes ActionApproval_Reject, the case management application will return to theFulReque Case Step. However, if the end user completes actionApproval_Approve, the case management application has resolved the caseand the application will reach the End Case Step.

FIGS. 22-24 depict GUIs displaying a completed event case managementapplication as an end user may see it. As depicted in FIG. 22, the enduser is presented with a form prompting them to submit informationincluding FirstName, LastName, AddressLine1, AddressLine2, State, andCity. This information will be used to resolve the event.

Thus, as described above, embodiments of the present invention providefor a tool for generating event case management applications. The toolrequires input of event case criteria, such as, but not limited to,event case type, steps, actions associated with the steps, actorsrequired to perform the actions, data entry documents/forms and/or dataentry fields in the documents/forms, and data entry points. Based on thereceived inputs and rules associated with the event case type and otherevent case criteria, the tool automatically generates computer code thatcreates an event case management application. As such, the tool providesa standardized and streamlined approach to generating event casemanagement applications that requires minimal technology support, iscost efficient and effectively delivers deployable event case managementapplications in minimal time.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible.

Those skilled in the art may appreciate that various adaptations andmodifications of the just described embodiments can be configuredwithout departing from the scope and spirit of the invention. Therefore,it is to be understood that, within the scope of the appended claims,the invention may be practiced other than as specifically describedherein.

1. A system for generating event case management applications, thesystem comprising: a first computing platform including a first memoryand at least one first processor in communication with the first memory;an event case management application rules database stored in the firstmemory, wherein the database stores rules for generating an event casemanagement application, wherein the rules are specific to at least casetype; a second computing platform including a second memory and at leastone second processor in communication with the second memory; and anevent case management application generator tool stored in the secondmemory, executable by the at least one second processor and configuredto: receive inputs that define criteria including case type for managingan event case, wherein an event case is defined a process for resolvingan event that requires a resolution; in response to receiving theinputs, access the rules database to obtain one or more rules specificto the case type; and apply the criteria and the one or more rulesspecific to at least the case type to automatically generate computercode that creates an application for managing the event case.
 2. Thesystem of claim 1, wherein the event case management applicationgenerator tool is further configured to receive the inputs that definethe criteria for managing the event case, wherein the inputs define aplurality of steps required to resolve the event.
 3. The system of claim3, wherein the event case management application generator tool isfurther configured to receive the inputs that define the criteria formanaging the event case, wherein the inputs include for each of theplurality of steps at least one of (i) a step identifier, (ii) an actorfor performing the step, (iii) actions required to perform the step, and(iv) an estimated time for completing the step.
 4. The system of claim3, wherein the event case management application rules database storesthe rules for generating the event case management application, whereinthe rules are specific to at least one of the actors for performing thesteps and the actions required to perform the steps.
 5. The system ofclaim 4, wherein the event case management application generator tool isfurther configured to: in response to receiving the user inputs, accessthe rules database to obtain one or more rules specific to at least oneof the actors for performing the steps or the actions required toperform the steps; and apply the user inputs and one or more rulesspecific to at least one of the actors required to perform the steps orthe actions required to perform the steps to automatically generatecomputer code that creates an application for managing the event case.6. The system of claim 2, wherein the event case management applicationgenerator tool is further configured to receive the inputs that definethe criteria for managing the event case, wherein the inputs define asequence for interconnecting the plurality of steps.
 7. The system ofclaim 6, wherein the event case management application generator tool isfurther configured to receive the inputs that define the criteria formanaging the event case, wherein the inputs include creating paths forinterconnecting the plurality of steps and the actions required toperform the steps.
 8. The system of claim 2, wherein the event casemanagement application generator tool is further configured to receivethe inputs that define the criteria for managing the event case, whereinthe inputs define one or more predetermined data entry documents and onemore data elements within each of the predetermined data entrydocuments.
 9. The system of claim 7, wherein the event case managementapplication generator tool is further configured to receive the inputsthat define the criteria for managing the event case, wherein the inputsdefine at least one of the steps or the actions that define the stepthat are associated with at least one of the one or more data entrydocuments or at least one of the data elements within the at least oneof the data entry documents.
 10. The system of claim 9, wherein theevent case management application rules database stores the rules forgenerating the event case management application, wherein the rules arespecific to at least one of the one or more data entry documents or theone or more data elements within the data entry documents.
 11. Thesystem of claim 10, wherein the event case management applicationgenerator tool is further configured to: in response to receiving theinputs, access the rules database to obtain one or more rules specificto at least one of the one or more data entry documents or the one ormore data elements within the data entry documents; and apply the userinputs and the one or more rules specific to the one or more data entrydocuments or the one or more data elements within the data entrydocuments to automatically generate computer code that creates anapplication for managing the event case.
 12. The system of claim 1,wherein the event case management application generator tool is furtherconfigured to generate the computer code that creates the applicationfor managing the event case, wherein the application includes aplurality of user interfaces for managing a workflow for processing theevent case.
 13. The system of claim 1, wherein the event case managementapplication generator tool is further configured to generate thecomputer code that creates the application for managing the event case,wherein the application includes a process model that defines the stepsand the actions required to perform the steps.
 14. Acomputer-implemented method for generating event case managementapplications, the method executed by one or more computing deviceprocessors and comprising: receiving inputs that define criteria,including case type, for managing an event case, wherein an event caseis defined a process for resolving an event that requires a resolution;in response to receiving the inputs, accessing a rules database toobtain one or more rules specific to at least the case type; andapplying the inputs and the one or more rules specific to at least thecase type to automatically generate computer code that creates anapplication for managing the event case.
 15. The method of claim 14,wherein receiving the inputs that define the criteria for managing theevent case further comprises receiving inputs that define a plurality ofsteps required to resolve the event and, for each of the steps, at leastone of (i) a step identifier, (ii) an actor for performing the step,(iii) actions required to perform the step, and (iv) an estimated timefor completing the step.
 16. The method of claim 14, wherein receivingthe inputs that define the criteria for managing the event case furthercomprises receiving inputs that define a sequence for interconnectingthe plurality of steps including creating paths for interconnecting theplurality of steps and the actions required to perform the steps. 17.The method of claim 14, wherein receiving the inputs that define thecriteria for managing the event case further comprises receiving inputsthat define one or more predetermined data entry documents and one moredata elements within each of the predetermined data entry documents andat least one of the steps or the actions associated with at least one ofthe one or more data entry documents or at least one of the dataelements within the at least one of the data entry documents.
 18. Themethod of claim 14, wherein in response to receiving the user inputs,accessing the rules database to obtain one or more rules furthercomprises accessing the rules database to obtain one or more rulesspecific to at least one of steps required to process the event case,actions required to perform the steps, actors required to perform theactions, data entry documents or data entry elements within thedocuments.
 19. A computer program product including a non-transitorycomputer-readable medium, the computer-readable medium comprising: afirst set of codes for causing a computer to receive inputs that definecriteria, including case type, for managing an event case, wherein anevent case is defined a process for resolving an event that requires aresolution; a second set of codes for causing a computer to, in responseto receiving the user inputs, access a rules database to obtain one ormore rules specific to at least the case type; and a third set of codesfor causing a computer to apply the criteria and the one or more rulesspecific to at least the case type to automatically generate computercode that creates an application for managing the event case.